Skip to content

Conversation

sakhisheikh
Copy link
Contributor

@sakhisheikh sakhisheikh commented Oct 9, 2025

Problem: It was only possible to navigate to next element

Solution

  • Made direction as configurable argument in the method call deviceInspectorMoveWithOptions
  • Move() is implemented that returns PlatformElementValue_V1 unique base64 identifier which could potentially be used to tap on element.
  • Added ReceiveMethodCallWithTimeout because ReceiveMethodCall expects the dtx message to be always arrived, reading channel inside ReceiveMethodCall becomes blocking forever

Reproducible Steps for blocking ReceiveMethodCall:

  • Enable Ax Inspector on home screen
  • Navigate to Previous element, ReceiveMethodCall will be blocked because no message is received on the reader channel.
  • hostInspectorCurrentElementChanged doesn't receive dtx message because AX inspector doesn't find an element in accessibility tree.

@sakhisheikh sakhisheikh requested a review from dmissmann October 10, 2025 13:44
@sakhisheikh sakhisheikh requested a review from dmissmann October 13, 2025 09:53
@dmissmann dmissmann merged commit b28efba into danielpaulus:main Oct 13, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants